<p>The following settings can be customized for each Export Action by administrative users on the <b>Export Actions</b> page in your <i>ExportZen Studio</i>, accessible via Site Settings / ExportZen Studio / Export Actions:</p><span>
</span><h4 class="rox-h4 rox-doctab rox-doctab-a"><a href="#" onclick="roxTogDocTab('a');">&quot;Menu Item and Integration&quot; tab:</a></h4><span class="rox-doctab rox-doctab-a">
<h3>Name for this Export Action</h3>
<p><b>(Text box)</b></p><p>This name will typically not be visible on content pages to end users, but helps you stay organized.</p>
<h3>This Export Action is...</h3>
<p><b>(Descriptor for a set of SharePoint Web Sites)</b></p><p>Optionally select in which web sites this Export Action will be available. By default, it will be available in all web sites and this usually does not need to be changed during your first explorations within this software. Only perform changes if you are familiar with the terminology presented in the above property editor. Should your changes not result in the expected outcome, you can always easily set this back to "all web sites, no exceptions" and then resume experimenting incrementally with your exceptions.</p>
<p>To define the set of Web Sites, first select either <b>Available in all Web Sites</b> or <b>Available in no Web Sites</b>, then click the <b>except...</b> link to describe which web sites to exclude from that selection. You can exclude:
<ul>
<li>the root Web Site (of the respectively-current Site Collection)</li>
<li>Web Sites based on the selected site definitions</li>
<li>or Web Sites with the specified titles, URL path fragments or IDs.</li>
</ul></p>
<h3>Show ExportZen menu item in the following Lists</h3>
<p><b>(Descriptor for a set of SharePoint Lists and Views)</b></p><p>Select in which Lists this export action will be offered as a menu item to end users (in the SharePoint 2007 "Actions" toolbar menu and in the SharePoint 2010 "Connect and Export" ribbon group (both only if the "ExportZen List Integration" Site Collection feature is activated too and for List Views, only with their Toolbar Type property set to Full or Show, not Summary or None).</p>
<p>To define the set of Lists, first select either <b>Show in all Lists</b> or <b>Show in no Lists</b>, then click the <b>except...</b> link to describe which Lists to exclude from that selection. You can exclude:
</p><ul>
<li>Lists of the selected base types</li>
<li>Lists of the selected template types</li>
<li>Lists of the selected base templates</li>
<li>or Lists with the specified names or IDs.</li>
</ul><p>
To define the set of Views, first select either <b>Show in all Views</b> or <b>Show in no Views</b>, then click the <b>except...</b> link to describe which Views to exclude from that selection. You can exclude:
<ul>
<li>the default View</li>
<li>hidden Views</li>
<li>personal Views</li>
<li>or Views with the specified names or IDs.</li>
</ul></p>
<h3>ExportZen menu item caption</h3>
<p><b>(Text box)</b></p><p>Specify the caption for this CSV export action to be shown in the export menu item for the Lists specified above. (If you do not specify a caption, the above name for this export action will be used, or if blank, its internal ID.)</p>
<p>Default value for new Export Actions:</p>
<pre>$Resources:Tool_ExportActions_DefTitle</pre>
<h3>ExportZen menu item description</h3>
<p><b>(Text box)</b></p><p>Specify the description for this CSV export action to be shown in the export menu item for the Lists specified above.</p>
</span><h4 class="rox-h4 rox-doctab rox-doctab-c"><a href="#" onclick="roxTogDocTab('c');">&quot;Column Layout and Export Contents&quot; tab:</a></h4><span class="rox-doctab rox-doctab-c">
<h3>Export columns</h3>
<p><b>(Text box)</b></p><p>Specify the List Columns (one per line) to include in that order in output CSV data files generated by this export action. (To rename a Column in the exported CSV, enter the List Column name, followed by a colon (:) and the CSV column name.) Be sure those Columns will be available in the exported List, otherwise the CSV column will remain empty.<br/><br/>If you clear this setting and keep it blank, the export will include <b>all</b> available View Columns shown.</p>
<p>Default value for new Export Actions:</p>
<pre>Title</pre>
<h3>Export all item version history in separate column</h3>
<p><b>(Text box)</b></p><p>Optional: if you&#39;d like ExportZen to append an additional column recording all version history per item (only for the Columns specified above, in a simple plain-text format), specify your preferred name for this CSV column here. Leave blank to not append a version history column.<br/><br/>Not applicable to <a target="_blank" href="http://SharePoint-Tools.net/PeopleZen/">User Profile exports via PeopleZen</a>.</p>
<h3>Export item version history in separate rows, one per version</h3>
<p><b>(Check box option)</b></p><p>Instead of keeping all version history in a single column, you can export each version in the history to its own row. These versions will appear underneath the data item row, in descending sort order, and in this case you&#39;ll need a separate CSV column to denote the version number of each history record. You <b>need</b> to enter this CSV column name (for example &#39;Version&#39;) above this check-box option if ticked.<br/><br/>Not applicable to <a target="_blank" href="http://SharePoint-Tools.net/PeopleZen/">User Profile exports via PeopleZen</a>.</p>
<h3>Export current View</h3>
<p><b>(Check box option)</b></p><p>If ticked, this export action only ever exports items included in the currently displayed List View, applying the View-defined default sort orders and filters (but <b>not</b> currently user-applied live sort order, filters or paging); otherwise, all List items are exported, unfiltered and in their original sort order.<br/><br/>Not applicable to <a target="_blank" href="http://SharePoint-Tools.net/PeopleZen/">User Profile exports via PeopleZen</a>.</p>
<h3>Ignore paging in PeopleZen exports</h3>
<p><b>(Check box option)</b></p><p>Even if the PeopleZen Web Part to be exported is paged, if this check-box option is ticked then all user profiles belonging to the Web Part are exported, instead of just those included in the currently shown page.</p>
<h3>Respect currently applied filters (FilterZen only)</h3>
<p><b>(Check box option)</b></p><p>If ticked, this export action only ever exports items included in the filtering currently applied to the applicable List View (<b>only</b> supports filters supplied by a currently connected <a target="_blank" href="http://roxority.com/filterzen/">FilterZen Filter Web Part</a>).</p>
</span><h4 class="rox-h4 rox-doctab rox-doctab-f"><a href="#" onclick="roxTogDocTab('f');">&quot;Formatting Options&quot; tab:</a></h4><span class="rox-doctab rox-doctab-f">
<h3>Use semicolons instead of commas</h3>
<p><b>(Check box option)</b></p><p>Not recommended unless you and your users intend to only ever open these CSV exports in Microsoft Office Excel <b>AND</b> Excel displays all comma-separated column values in a single cell (some internationalized Excel versions do that, some don&#39;t).</p>
<h3>Apply UNIX-style escaping</h3>
<p><b>(Check box option)</b></p><p>If un-ticked, ExportZen generates CSV data files using escaping patterns (for critical characters such as commas, line-breaks and quotes) that software written for Windows or Office is more likely to read flawlessly. Tick this check box to generate CSV data files using UNIX-style escaping patterns instead (only recommended if you get errors while feeding your exported CSV data files to other, non-Office software).</p>
<h3>Export locale</h3>
<p><b>(Culture picker)</b></p><p>This setting controls how numbers and dates are represented in this export. For example, dates may be stored in an US format (due to your SharePoint installation) but your export consumers may use a different-locale version of Excel (such as for example German), which would then mis-read and mis-represent factually-correct, but US-formatted date values. Keep the default choice to start with and experiment as needed if results do not meet expectations.</p>
<p>The drop-down menu provides all standard-defined regions. You can also choose from the following "dynamic" cultures:
</p><ul>
<li>Server-side &#39;current&#39; locale &mdash; the culture currently set to use by default for the Windows and/or ASP.NET installation on the server</li>
<li>Web site locale &mdash; the culture selected under Site Settings / Regional Settings</li>
<li>User account locale &mdash; the culture selected for the current end user account unter My Settings / Regional Settings</li>
<li>Server-side installation locale &mdash; the culture of the Windows installation on the server</li>
<li>User agent (browser) locale &mdash; the browser-supplied &#39;preferred culture&#39; hint</li>
</ul>
<p>The default choice is: <i>Server-side &#39;current&#39; locale</i>.</p>
<h3>Export encoding</h3>
<p><b>(Encoding picker)</b></p><p>Only if your exports contain international characters that don&#39;t look as expected in external software importing this export should you start experimenting with different export encodings. The Unicode / UTF encodings are the recommended choices to test before trying other encodings. Keep this set to Default <b>UNLESS</b> your exported contents are not decoded correctly by external software that needs to consume this export in production.</p>
<p>The drop-down menu provides all standard-defined text encodings. The default choice is: <i>Server-side default encoding</i>, meaning the default encoding defined for the Windows and/or ASP.NET installation on the server.</p>
<h3>Prepend UTF-8 byte order mark</h3>
<p><b>(Check box option)</b></p><p><b>ONLY</b> tick this option if you selected the UTF-8 encoding above <b>AND</b> your exported contents are not decoded correctly by the external software that needs to consume this export in production. Recommended for opening UTF-8 exports in Excel.</p>
</span>
